In order to assist folks upgrading we are now going to maintain a
document describing information critical to existing Apache users. Note
that it only lists differences between recent major releases, so
for example, folks using Apache 1.1 or earlier will have to figure out
what changed up to Apache 1.2 before this document can be considered
relevant. Old users could look at the src/CHANGES
file
which tracks code changes.
These are intended to be brief notes, and you should be able to find
more information in either the New Features
document, or in the src/CHANGES
file.
Module
directive has been changed to the
AddModule
directive.
Configuration
variable EXTRA_LFLAGS
has
been renamed EXTRA_LDFLAGS
.
-DMAXIMUM_DNS
definition has been obsoleted by
changes to mod_access
enforcing double-reverse DNS lookups
when necessary.
mod_dir
has been split into two pieces
mod_autoindex
, and
mod_dir
.
mod_browser
has been
replaced by mod_setenvif
.
suexec
,
or adding -DUSE_FCNTL_SERIALIZED_ACCEPT
to
EXTRA_CFLAGS
. This is slower, more information is available
on the performance tuning
page. There is a mild denial of service attack possible with the
default config, but the default config is an order of magnitude faster.
mod_auth_msql
has been removed from the distribution.
NameVirtualHost
directive. Previously this support was
given implicitly on the "main server address". Now it has to be
explicitly listed so as to avoid many problems that users had.
Please see the Apache Virtual Host
documentation for further details on configuration.
HostnameLookups
defaults to Off.
mod_access
syntax "allow user-agents" was removed. The replacement is the
more general "allow from env".
<Directory>
directives,
for example.
TransferLog
directive is given then nothing will
be logged.
(Previously it would default to logs/access_log
.)
ServerType inetd
has been deprecated. It still exists,
but bugs are unlikely to be fixed.
httpd_monitor
has been deprecated. The replacement is
to use mod_status
and make a request to a URL such as
http://myhost/server-status?refresh=10
.
"nph-" CGIs, which formerly provided a direct socket to the client without any server post-processing, were not fully compatible with HTTP/1.1 or SSL support. As such they would have had to implement the transport details, such as encryption or chunking, in order to work properly in certain situations. Now, the only difference between nph and non-nph scripts is "non-parsed headers".
dbmmanage
has been overhauled.